Network apparatus and method therefor

ABSTRACT

A network apparatus ( 10, 30 ) incorporates edge computing related control information ( 1001, 1101 ) into a header part ( 800 ) of a protocol data unit of an encapsulation protocol that is used to encapsulate a user packet originated from or destined for a radio terminal. Further, the network apparatus ( 10 ) transmits the protocol data unit whose header part ( 800 ) contains the edge computing related control information ( 1001, 1101 ).

TECHNICAL FIELD

The present disclosure relates to a mobile communication network and, inparticular, to an apparatus and a method for edge computing.

BACKGROUND ART

The European Telecommunications Standards Institute (ETSI) has startedstandardization of Mobile Edge Computing (MEC) (see Non-PatentLiterature 1). The ETSI MEC Industry Specification Group (ISG) haschanged its name from “Mobile Edge Computing” to “Multi-access EdgeComputing”. For example, the MEC offers, to application developers andcontent providers, cloud-computing capabilities and an informationtechnology (IT) service environment in a Radio Access Network (RAN) inclose proximity to mobile subscribers. This environment providesultra-low latency and high bandwidth as well as direct access to radionetwork information (e.g., subscriber's location and cell load) that canbe leveraged by applications and services.

The MEC is based on a virtualized platform, similar to Network FunctionVirtualization (NFV). While NFV focuses on network functions, MECenables applications (referred to as mobile edge applications) to be runat the edge of the network. The MEC server is an entity(ies) including aplatform and virtualization infrastructure for providing mobile edgeapplications with computing resources, storage resources, and networkresources. The MEC server may also be referred to as a mobile edge hostor a mobile edge cloud.

The Third Generation Partnership Project (3GPP) has stared a study on asolution similar to MEC. This solution is referred to as “Context AwareService Delivery in RAN” (see Non-Patent Literature 2). The ContextAware Service Delivery in RAN enables a cache server for context awareservice delivery to be deployed at the edge of a mobile communicationnetwork. Further, one of the requirements for the Next Generation RadioAccess Technologies currently studied by the 3GPP is that the RANarchitecture shall allow for deployment flexibility (see Non-PatentLiterature 3). This deployment flexibility allows, for example, a hostrelevant RAN, a core network (CN), and application functions to bedeployed at the edge of the RAN to enable context aware service deliveryand low latency services.

Patent Literature 1 discloses that the General Packet Radio Service(GPRS) Tunneling Protocol for User Plane (GTP-U) protocol is used inorder for a Long Term Evolution (LTE) base station (i.e., eNB) totransmit and receive user data to and from an application server (i.e.,MEC server) located at the RAN edge.

CITATION LIST Patent Literature

-   Patent Literature 1: International Patent Publication No. WO    2016/174864

Non Patent Literature

-   Non-Patent Literature 1: ETSI GS MEC 002 V1.1.1 (2016-03) “Mobile    Edge Computing (MEC); Technical Requirements”, March 2016-   Non-Patent Literature 2: 3GPP TR 36.933 V14.0.0 (2017-03) “3rd    Generation Partnership Project; Technical Specification Group Radio    Access Network; Study on Context Aware Service Delivery in RAN for    LTE; (Release 14)”, March 2017-   Non-Patent Literature 3: 3GPP TR 38.913 V14.2.0 (2017-03) “3rd    Generation Partnership Project; Technical Specification Group Radio    Access Network; Study on Scenarios and Requirements for Next    Generation Access Technologies; (Release 14)”, March 2017

SUMMARY OF INVENTION Technical Problem

It may be preferable that the MEC server be able to use an interface forexchanging MEC-related control information with a node in the mobilecommunication network. The MEC-related control information includes, forexample, radio network information to be sent from the mobilecommunication network to the MEC server, or network control request tobe sent from the MEC server to the mobile communication network, orboth. The node in the mobile communication network may be a RAN node(e.g., eNB or Radio Network Controller (RNC)) or a core network node(e.g., S-GW or Packet Data Network (PDN) Gateway (P-GW)). Alternatively,the node in the mobile communication network may be a gateway for localbreakout (e.g., Local Gateway (L-GW) for Local IP Access (LIPA), L-GWfor Selected IP Traffic Offload (SIPTO) at the Local Network, andStandalone Gateway for SIPTO at the Local Network).

Note that, as described above, Patent Literature 1 discloses that theLTE eNB uses the GTP-U protocol to transmit and receive user data to andfrom the MEC server. However, Patent Literature 1 does not explicitlydisclose an interface used by a node (e.g., eNB) in the mobilecommunication network to exchange MEC-related control information withthe MEC server.

One of the objects to be attained by embodiments disclosed herein is toprovide an apparatus, a method, and a program that enable a MEC entity(e.g., MEC server) and a network node (e.g., base station, gateway) toexchange MEC-related control information with each other in anuncomplicated manner. The above-described object is merely one of theobjects to be attained by the embodiments disclosed herein. Otherobjects or problems and novel features will be made apparent from thefollowing description and the accompanying drawings.

Solution to Problem

In a first aspect, a network apparatus includes at least one memory andat least one processor coupled to the at least one memory. The at leastone processor is configured to: incorporate edge computing relatedcontrol information into a header part of a protocol data unit of anencapsulation protocol that is used to encapsulate a user packetoriginated from or destined for a radio terminal; and transmit theprotocol data unit whose header part contains the edge computing relatedcontrol information.

In a second aspect, a method for a network apparatus includes: (a)incorporating edge computing related control information into a headerpart of a protocol data unit of an encapsulation protocol, theencapsulation protocol being used to encapsulate a user packetoriginated from or destined for a radio terminal; and (b) transmittingthe protocol data unit whose header part contains the edge computingrelated control information.

In a third aspect, a program includes a set of instructions (softwarecodes) that, when loaded into a computer, causes the computer to performa method for a network apparatus. The method includes incorporating edgecomputing related control information into a header part of a protocoldata unit of an encapsulation protocol, the encapsulation protocol beingused to encapsulate a user packet originated from or destined for aradio terminal.

Advantageous Effects of Invention

According to the above-described aspects, it is possible to provide anapparatus, a method, and a program that enable a MEC entity (e.g., MECserver) and a network node (e.g., a base station, and a gateway) toexchange MEC-related control information with each other in anuncomplicated manner.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram showing a configuration example of a mobilecommunication network according to an embodiment;

FIG. 2 is a diagram showing a configuration example of a mobilecommunication network according to an embodiment;

FIG. 3 is a diagram showing a configuration example of a mobilecommunication network according to an embodiment;

FIG. 4 is a diagram showing a configuration example of a mobilecommunication network according to an embodiment;

FIG. 5 is a diagram showing a configuration example of a mobilecommunication network according to an embodiment;

FIG. 6 is a diagram showing a configuration example of a mobilecommunication network according to an embodiment;

FIG. 7 is a diagram showing a configuration example of a mobilecommunication network according to an embodiment;

FIG. 8 is a diagram showing a configuration example of a GTP-U headeraccording to an embodiment;

FIG. 9 is a diagram showing an example of a next extension header typeaccording to an embodiment;

FIG. 10 is a diagram showing an example of an extension header accordingto an embodiment;

FIG. 11 is a diagram showing an example of an extension header accordingto an embodiment;

FIG. 12 is a sequence diagram showing an example of signaling betweeneNB/gNB and a MEC server according to an embodiment;

FIG. 13 is a diagram showing a configuration example of an eNB accordingto an embodiment;

FIG. 14 is a diagram showing a configuration example of an S-GWaccording to an embodiment; and

FIG. 15 is a diagram showing a configuration example of a MEC serveraccording to an embodiment.

DESCRIPTION OF EMBODIMENTS

Specific embodiments will be described hereinafter in detail withreference to the drawings. The same or corresponding elements aredenoted by the same symbols throughout the drawings, and duplicatedexplanations are omitted as necessary for the sake of clarity.

Configuration examples of a mobile communication network according toembodiments are described with reference to FIGS. 1 to 7. FIGS. 1 to 3show examples of deployment of an LTE system and a MEC server coupledthereto. In the example of FIG. 1, an eNB 10 communicates with an S-GW20 and a MEC server 30. As is well known, the eNB 10 is a node in a RAN(i.e., Evolved Universal Terrestrial Radio Access Network (E-UTRAN)),while the S-GW 20 is a node in a core network (i.e., Evolved Packet Core(EPC)). The MEC server 30 is coupled to the eNB 10. The MEC server 30may be located in the same site as the eNB 10.

As described above, the MEC server 30 is an entity(ies) including aplatform and virtualization infrastructure for providing mobile edgeapplications with computing resources, storage resources, networkresources, or any combination thereof. The MEC server 30 may also bereferred to as a mobile edge host or a mobile edge cloud. Further, theMEC server 30 may be referred to as an Internet of Things (IoT) serviceenabler.

The eNB 10 uses the GTP-U protocol to send uplink user packets of aradio terminal (i.e., User Equipment (UE)) to a P-GW (not shown) throughthe S-GW 20, and to receive downlink user packets from the P-GW (notshown) through the S-GW 20. The downlink user packets and the uplinkuser packets are typically Internet Protocol (IP) packets. Further, inthe example of FIG. 1, the eNB 10 also uses the GTP-U protocol totransfer user packets to be transmitted between a mobile edgeapplication instantiated on the MEC server 30 and a UE applicationrunning in a UE.

Furthermore, in the example of FIG. 1, the eNB 10 also uses the GTP-Uprotocol to send MEC-related control information to the MEC server 30and to receive MEC-related control information from the MEC server 30.Specifically, each of the eNB 10 and the MEC server 30 is configured toincorporate MEC-related control information into a header part (i.e.,GTP-U header) of a GTP Protocol Data Unit (GTP-PDU), and transmit theGTP-PDU whose header part contains the MEC-related control information.The details of enhancements or improvements to the GTP-U protocol toallow for sending MEC-related control information will be describedlater.

The MEC-related control information to be sent from the eNB 10 to theMEC server 30 may include measurement information about the mobilecommunication network. Specifically, the MEC-related control informationto be sent from the eNB 10 to the MEC server 30 may include at least oneof: radio interface quality; cell throughput; or backhaul throughput.The radio interface quality may include, for example, a downlink channelquality measured by a UE or an uplink channel quality measured by theeNB 10, or both. The radio interface quality may be a Received SignalStrength Indicator (RSSI), a Channel Quality Indicator (CQI), ReferenceSignal Received Power (RSRP), Reference Signal Received Quality (RSRQ),or any combination thereof.

Additionally or alternatively, the MEC-related control information to besent from the eNB 10 to the MEC server 30 may include UE information.The UE information indicates, for example, one or both of informationabout a service used by a UE and priority information of a UE. Theinformation about a service may include a service type or Quality ofService (QoS), or both. More specifically, the information about aservice may be information related to video contents used by a UE.Additionally or alternatively, the UE information may include variousinformation items about characteristics of a UE, for example, locationinformation, security information, charging information, bearerinformation, or mobility characteristics (e.g., high speed, low speed,movement frequency) of the UE.

The MEC-related control information to be sent from the MEC server 30 tothe eNB 10 may be a radio resource control request. The radio resourcecontrol request requests the eNB 10 to adjust radio resource managementor radio resource scheduling in the RAN. The MEC server 30 may generatea radio resource control request based on the MEC-related controlinformation (e.g., radio interface quality, priority of a UE, orcharacteristics of a UE) received from the eNB 10. For example, theradio resource control request may request the eNB 10 to release a radioconnection(s) (i.e., Radio Resource Control (RRC) connection) of one ormore UEs, or to perform an inter-cell or inter-Radio Access Technology(Inter-RAT) handover of one or more UEs. For example, the radio resourcecontrol request may request the eNB 10 to adjust a scheduling metricapplied to one or more UEs.

Additionally or alternatively, the MEC-related control information to besent from the MEC server 30 to the eNB 10 may be a traffic controlrequest. The traffic control request requests the eNB 10 to adjusttraffic control for user packets to be sent from the eNB 10 to the corenetwork (i.e., the S-GW 20) or the MEC server 30. For example, thetraffic control request may request the eNB 10 to perform trafficshaping on user packets to be sent from the eNB 10 to the core network(i.e., the S-GW 20) or the MEC server 30. The traffic control requestmay indicate an identifier (e.g., UE identifier, or Tunnel EndpointIdentifier (TEID)) related to a packet flow to be subjected to theshaping, flow priority, or a packet transmission rate (e.g., committedinformation rate (CIR)), or any combination thereof.

In the example of FIG. 2, the MEC server 30 uses the GTP-U protocol tocommunicate with the S-GW 20, which is a core network node. The S-GW 20shown in FIG. 2 may be a gateway for local breakout. Specifically, theS-GW 20 may be a standalone GW for SIPTO at the Local Network. Thestandalone GW includes at least user plane functions of the S-GW anduser plane functions of the P-GW.

In FIG. 2, similarly to the example of FIG. 1, the eNB 10 may use theGTP-U protocol to transfer user packets to be transmitted between amobile edge application instantiated on the MEC server 30 and a UEapplication running in a UE. The user packets are transferred betweenthe eNB 10 and the MEC server 30 through a GTP tunnel between the eNB 10and the S-GW 20 and through a GTP tunnel between the S-GW 20 and the MECserver 30.

Furthermore, in the example of FIG. 2, the S-GW 20 uses the GTP-Uprotocol to send MEC-related control information to the MEC server 30and to receive MEC-related control information from the MEC server 30.The MEC-related control information may be exchanged between the eNB 10and the MEC server 30. In other words, the S-GW 20 may relay theMEC-related control information between the eNB 10 and the MEC server30.

In the example of FIG. 3, the MEC server 30 is located between the eNB10 and the S-GW 20. In this case, the above-described user packets aretransferred between the eNB 10 and the S-GW 20 through a GTP tunnelbetween the eNB 10 and the MEC server 30 and through a GTP tunnelbetween the MEC server 30 and the S-GW 20.

FIGS. 4 to 7 show examples of deployment of the fifth generation mobilecommunication system (5G) and a MEC server coupled thereto. The 3GPP hasstarted in 2016 the standardization for 5G, i.e., 3GPP Release 14, tomake it a commercial reality in 2020 or later. 5G is expected to berealized by continuous enhancement/evolution of LTE and LTE-Advanced andan innovative enhancement/evolution by an introduction of a new 5G airinterface (i.e., a new Radio Access Technology (RAT)). The new RATsupports, for example, frequency bands higher than the frequency bands(e.g., 6 GHz or lower) supported by LTE/LTE-Advanced and its continuousevolution. For example, the new RAT supports centimeter-wave bands (10GHz or higher) and millimeter-wave bands (30 GHz or higher).

In this specification, the fifth generation mobile communication systemis referred to as a 5G System or a Next Generation (NextGen) System (NGSystem). The new RAT for the 5G System is referred to as a New Radio(NR), a 5G RAT, or a NG RAT. A new Radio Access Network (RAN) for the 5GSystem is referred to as a 5G-RAN or a NextGen RAN (NG RAN). A new basestation in the 5G-RAN is referred to as a gNodeB (gNB) or a NR NodeB (NRNB). A new core network for the 5G System is referred to as a 5G CoreNetwork (5GC) or a NextGen Core (NG Core). A radio terminal (UE) capableof being connected to the 5G System is referred to as a 5G UE or aNextGen UE (NG UE), or simply referred to as a UE. The official names ofthe RAT, UE, radio access network, core network, network entities(nodes), protocol layers and the like for the 5G System will bedetermined in the future as standardization work progresses.

In the example of FIG. 4, a gNB 40 communicates with a user planefunction (UPF) 50 and the MEC server 30. The gNB 40 is a node in the 5GRAN. The interface between the 5G RAN (the gNB 40) and the UPF 50 isreferred as to an N3 interface (or reference point). The MEC server 30is coupled to the gNB 40. The MEC server 30 may be located in the samesite as the gNB 40.

The gNB 40 may be implemented based on a Cloud Radio Access Network(C-RAN) concept. That is, as shown in FIG. 4, the gNB 40 may include aCentral Unit (CU) 42 and at least one Distributed Unit (DU) 44. The CU42 is also referred to as a Baseband Unit (BBU) or a Central Unit (CU).The DU 44 is also referred to as a Radio Unit (RU), a Remote Radio Head(RRH), a Remote Radio Equipment (RRE), or a Transmission and ReceptionPoint (TRP or TRxP). In the example of FIG. 4, the MEC server 30 usesthe GTP-U protocol to communicate with the CU 42.

The gNB 40 (the CU 42) uses the GTP-U protocol to send uplink userpackets of the UE to the UPF 50 and to receive downlink user packetsfrom the UPF 50. The downlink user packets and the uplink user packetsare typically Internet Protocol (IP) packets. Further, in the example ofFIG. 4, the gNB 40 (the CU 42) also uses the GTP-U protocol to transferuser packets to be transmitted between a mobile edge applicationinstantiated on the MEC server 30 and a UE application running in a UE.

Furthermore, in the example of FIG. 4, the gNB 40 (the CU 42) also usesthe GTP-U protocol to send MEC-related control information to the MECserver 30 and to receive MEC-related control information from the MECserver 30. Specifically, each of the gNB 40 (the CU 42) and the MECserver 30 is configured to incorporate MEC-related control informationinto a header part (i.e., GTP-U header) of a GTP-PDU, and transmit theGTP-PDU whose header part contains the MEC-related control information.The details of enhancements or improvements to the GTP-U protocol toallow for sending MEC-related control information will be describedlater.

In the example of FIG. 5, the MEC server 30 uses the GTP-U protocol tocommunicate with the UPF 50, which is a core network node. The UPF 50shown in FIG. 5 may be a gateway for local breakout. Specifically, theUPF 50 may be located at the edge of the 5G RAN to enable context awareservice delivery and low latency services.

In FIG. 5, similarly to the example of FIG. 4, the gNB 40 (the CU 42)may use the GTP-U protocol to transfer user packets to be transmittedbetween a mobile edge application instantiated on the MEC server 30 anda UE application running in a UE. The user packets are transferredbetween the gNB 40 and the MEC server 30 through a GTP tunnel betweenthe gNB 40 and the UPF 50 and through a GTP tunnel between the UPF 50and the MEC server 30.

Furthermore, in the example of FIG. 5, the UPF 50 uses the GTP-Uprotocol to send MEC-related control information to the MEC server 30and to receive MEC-related control information from the MEC server 30.The MEC-related control information may be exchanged between the gNB 40and the MEC server 30. In other words, the UPF 50 may relay theMEC-related control information between the gNB 40 and the MEC server30.

The configuration example of FIG. 6 is a modification of theconfiguration example shown in FIG. 4, and clearly indicates that theMEC server 30 is located in the same site as the gNB 40. Meanwhile, theconfiguration example of FIG. 7 shows a modification of theconfiguration example of FIG. 6. In the configuration example of FIG. 7,the MEC server 30 sends downlink user packets from a mobile edgeapplication to a UE through the DU 44 (and not through the CU 42), andreceives uplink user packets from the UE through the DU 44 (and notthrough the CU 42). In the example of FIG. 7, the DU 44 supports theuser plane protocol stack of the 5G RAN including a Packet DataConvergence Protocol (PDCP).

Instead of the configuration examples shown in FIGS. 4 to 7, the MECserver 30 may be located between the gNB 40 and the UPF 50. In thiscase, the above-described user packets are transferred between the gNB40 and the UPF 50 through a GTP tunnel between the gNB 40 and the MECserver 30 and through a GTP tunnel between the MEC server 30 and the UPF50.

The embodiments according to FIGS. 1 to 7 provide the examples in whichthe GTP-U protocol is used. However, the GTP-U protocol is merely anexample of an encapsulation protocol for encapsulating user packetsoriginated from or destined for a UE. The embodiments according to FIGS.1 to 7 may be modified to use an encapsulation protocol different fromthe GTP-U protocol. For example, the 5G system, the standardization ofwhich is currently underway, may use an encapsulation protocol differentfrom the GTP-U protocol to transfer user data in the 5G network. Theencapsulation protocol can be referred to as a tunneling protocol.

As can be understood from the above description, in the embodimentsaccording to FIGS. 1 to 7, the network apparatus (e.g., eNB 10, S-GW 20,MEC server 30, gNB 40, CU 42, or UPF 50) incorporates MEC-relatedcontrol information into a header part of a PDU of an encapsulationprotocol that is used to encapsulate user packets originated from ordestined for a UE. Further, the network apparatus transmits theencapsulation protocol PDU whose header part contains the MEC-relatedcontrol information. Accordingly, in the embodiments according to FIGS.1 to 7, the encapsulation protocol for transferring user packets betweenthe RAN and the core network can also be used to send the MEC-relatedcontrol information. The embodiments according to FIGS. 1 to 7 thusenable the MEC server 30 and the network node (e.g., eNB 10, S-GW 20,gNB 40, or UPF 50) to exchange the MEC-related control information witheach other in an uncomplicated manner.

The following provides details of the enhancements or improvements tothe GTP-U protocol to allow for sending the MEC-related controlinformation with reference to FIGS. 8 to 11. FIG. 8 shows aconfiguration of a GTP-U header 800 contained in the GTP-PDU. TheGTP-PDU is also referred to as a GTP-U message. The GTP-PDU is either aG-PDU or a signaling message. The G-PDU is used to carry a User datapacket (i.e., a Transport PDU (T-PDU)). The G-PDU consists of a Userdata packet (T-PDU) and a GTP-U header. Meanwhile, unlike the G-PDU, thesignaling message is a control message sent between the GTP-U tunnelendpoints to perform path management or tunnel management. The signalingmessage consists of a GTP-U header and zero or more Information Elements(IEs).

A message type field 801 in the GTP-U header 800 indicates a type of theGTP-PDU (i.e., GTP-U message). For example, when the GTP-U message is aG-PDU (i.e., GTP-PDU carrying a user IP packet), the message type field801 has a decimal value of 255. On the other hand, when the GTP-Umessage is a signaling message, the message type field 801 has a decimalvalue of 1, 2, 26, 31, or 254. When the message type value (decimal) is1, 2, 26, 31, or 254, the GTP-U message is an Echo Request for pathmanagement, an Echo Response for path management, an Error Indicationfor tunnel management, a Supported Extension Headers Notification forpath management, or an End Marker for tunnel management.

In some implementations, the GTP-U header 800 of the GTP-PDU carryingthe MEC-related control information may include the message type field801 having a decimal value of 255 corresponding to the G-PDU. Further,an extension header 803 may be used to carry the MEC-relatedinformation. The extension header 803 is included in the GTP-U header800. A next extension header type field 802 indicates a type of anextension header following it. When a decimal value of 255 correspondingto the G-PDU is set in the GTP-U header 800 of the GTP-PDU carrying theMEC-related control information, the GTP-PDU may not include a payloadcontaining a User data packet (i.e., Transport PDU (T-PDU)).

FIG. 9 shows a specific example of the values to be set in the nextextension header type field 802. In the example of FIG. 9, two valuesindicating the MEC-related control information have been newly defined.In the example of FIG. 9, the value of “1000 1000” indicates that thetype of the extension header is a MEC Container from eNB/gNB extensionheader 901. Similarly, the value of “1000 1001” indicates that the typeof the extension header is a MEC Container from MEC server extensionheader 902. The MEC Container from eNB/gNB extension header 901 containsa MEC Container from eNB/gNB that carries the MEC-related controlinformation to be sent from the eNB 10 or the gNB 40 to the MEC server30. The MEC Container from MEC server extension header 902 contains aMEC Container from MEC server that carries the MEC-related controlinformation to be sent from the MEC server 30 to the eNB 10 or the gNB40.

FIG. 10 shows a specific example of the MEC Container from eNB/gNBextension header 901. The MEC Container from eNB/gNB extension header901 contains a MEC Container from eNB/gNB field 1001. The MEC Containerfrom eNB/gNB field 1001 indicates, for example, at least one of: a MECIdentifier; radio interface quality (Air Information); uplink cellthroughput (UL Cell Throughput); downlink cell throughput (DL CellThroughput); uplink backhaul throughput (UL Backhaul Throughput); downlink backhaul throughput (DL Backhaul Throughput); or UE information.The MEC identifier identifies a session related to the MEC between theeNB/gNB and the MEC server.

FIG. 11 shows a specific example of the MEC Container from MEC serverextension header 902. The MEC Container from MEC server extension header902 contains a MEC Container from MEC server field 1101. The MECContainer from MEC server field 1101 indicates, for example, at leastone of: a MEC identifier; a Radio Scheduler Configuration; or TrafficControl parameters.

Using the extension header in the GTP-U header to carry the MEC-relatedcontrol information provides, for example, the following advantage. TheGTP-U protocol specifies that when a GTP entity does not support amandatory extension header, the GTP entity sends a “Supported ExtensionHeaders Notification” to the peer GTP entity. The “Supported ExtensionHeaders Notification” is a signaling message for path management andindicates a list of extension header types supported by a transmissionsource GTP entity. Further, the GTP-U protocol specifies that when a GTPentity receives an unsupported extension header, the GTP entity ignoresthe received extension header. Thus, the above-described implementationin which the extension header in the GTP-U header is used to carry theMEC-related control information can contribute to the stabilization ofthe operation of the network.

FIG. 12 is a sequence diagram showing a process 1200 that is an exampleof signaling between the eNB 10 (or the gNB 40) and the MEC server 30.In Step 1201, the eNB 10 (or the gNB 40) sends, to the MEC server 30, aMEC Container from eNB/gNB carrying MEC-related control information. TheMEC-related control information carried by the MEC Container fromeNB/gNB includes, for example, a measured value(s) of one or morequality parameters (e.g., CQI, cell throughput, backhaul throughput).The eNB 10 (or the gNB 40) may periodically send the MEC Container fromeNB/gNB of Step 1201, or may aperiodically send it in response to apredetermined trigger event. In Step 1202, the MEC server 30 sends, tothe eNB 10 (or the gNB 40), a MEC Container from MEC server carryingMEC-related control information. As described above, the MEC-relatedcontrol information carried by the MEC Container from MEC server mayinclude a radio resource control request or a traffic control request.

The following provides configuration examples of the eNB 10, the S-GW20, the MEC server 30, the gNB 40, the CU 42, and the UPF 50 accordingto the above-described embodiments. FIG. 13 is a block diagram showing aconfiguration example of the eNB 10. The configuration of the gNB 40 maybe similar to that of FIG. 13. Referring to FIG. 13, the eNB 10 includesa Radio Frequency (RF) transceiver 1301, a network interface 1303, aprocessor 1304, and a memory 1305. The RF transceiver 1301 performsanalog RF signal processing to communicate with a UE. The RF transceiver1301 may include a plurality of transceivers. The RF transceiver 1301 iscoupled to an antenna 1302 and the processor 1304. The RF transceiver1301 receives modulated symbol data (or OFDM symbol data) from theprocessor 1304, generates a transmission RF signal, and supplies thetransmission RF signal to the antenna 1302. Further, the RF transceiver1301 generates a baseband reception signal based on a reception RFsignal received by the antenna 1302 and supplies it to the processor1304.

The network interface 1303 is used to communicate with network nodes(e.g., the S-GW 20, the MEC server 30, and a Mobility Management Entity(MME)). The network interface 1303 may include, for example, a networkinterface card (NIC) conforming to the IEEE 802.3 series.

The processor 1304 performs digital baseband signal processing (i.e.,data-plane processing) and control-plane processing for radiocommunication. For example, in the case of LTE or LTE-Advanced, thedigital baseband signal processing performed by the processor 1304 mayinclude signal processing of Packet Data Convergence Protocol (PDCP),Radio Link Control (RLC), Medium Access Control (MAC), and physical(PHY) layers. Further, the control-plane processing performed by theprocessor 1304 may include processing of S1-MME, GTP-U, and RadioResource Control (RRC) protocols and processing of MAC Control Elements(MAC CEs).

The processor 1304 may include a plurality of processors. The processor1304 may include, for example, a modem processor (e.g., a Digital SignalProcessor (DSP)) that performs digital baseband signal processing and aprotocol stack processor (e.g., a Central Processing Unit (CPU) or aMicro Processing Unit (MPU)) that performs the control-plane processing.

The memory 1305 is composed of a volatile memory and a non-volatilememory. The memory 1305 may include a plurality of memory devices thatare physically independent from each other. The volatile memory is, forexample, a Static Random Access Memory (SRAM), a Dynamic RAM (DRAM), ora combination thereof. The non-volatile memory is, for example, a maskRead Only Memory (MROM), an Electrically Erasable Programmable ROM(EEPROM), a flash memory, a hard disc drive, or any combination thereof.The memory 1305 may include a storage located apart from the processor1304. In this case, the processor 1304 may access the memory 1305through the network interface 1303 or an I/O interface (not shown).

The memory 1305 may store one or more software modules (computerprograms) 1306 including instructions and data to perform processing bythe eNB 10 described in the above-described embodiments. In someimplementations, the processor 1304 may be configured to load thesoftware modules 1306 from the memory 1305 and execute the loadedsoftware modules, thereby performing processing of the eNB 10 describedin the above-described embodiments with reference to the sequencediagrams and the flowcharts.

FIG. 14 is a block diagram showing a configuration example of the S-GW20. The configurations of the CU 42 and the UPF 50 may be similar tothat of FIG. 14. Referring to FIG. 14, the S-GW 20 includes a networkinterface 1401, a processor 1402, and a memory 1403. The networkinterface 1401 is used to communicate with network nodes (e.g., the eNB10, the MEC server 30, the P-GW, and an MME). The network interface 1401may include, for example, a network interface card (NIC) conforming tothe IEEE 802.3 series.

The processor 1402 may be configured to load software (computerprogram(s)) from the memory 1403 and execute the loaded software,thereby performing processing of the S-GW 20 described in the aboveembodiments. The processor 1402 may be, for example, a microprocessor,an MPU, or a CPU. The processor 1402 may include a plurality ofprocessors.

The memory 1403 is composed of a volatile memory and a non-volatilememory. The memory 1403 may include a plurality of memory devices thatare physically independent from each other. The non-volatile memory is,for example, an MROM, a PROM, a flash memory, a hard disc drive, or anycombination thereof. The memory 1403 may include a storage located apartfrom the processor 1402. In this case, the processor 1402 may access thememory 1403 through the network interface 1401 or an I/O interface (notshown).

The memory 1403 may store one or more software modules (computerprograms) 1404 including instructions and data to perform processing bythe S-GW 20 described in the above embodiments. In some implementations,the processor 1402 may be configured to load the software modules 1404from the memory 1403 and execute the loaded software modules, therebyperforming processing of the S-GW 20 described in the above embodiments.

FIG. 15 is a block diagram showing a configuration example of the MECserver 30. Referring to FIG. 15, the MEC server 30 includes hardwarecomponents including a network interface 1501, a processor 1502, and amemory (or a storage) 1503. The network interface 1501 is used tocommunicate with a network node (e.g., the eNB, the S-GW 20, the gNB 40,the CU 42, the DU 44, or the UPF 50). The network interface 1501 mayinclude, for example, a network interface card (NIC) conforming to theIEEE 802.3 series.

The processor 1502 may be configured to load software (computerprogram(s)) from the memory 1503 and execute the loaded software,thereby performing processing of the MEC server 30 described in theabove embodiments. The processor 1502 may be, for example, amicroprocessor, an MPU, or a CPU. The processor 1502 may include aplurality of processors.

The memory 1503 is composed of a volatile memory and a non-volatilememory. The memory 1503 may include a plurality of memory devices thatare physically independent from each other. The memory 1503 may includea storage located apart from the processor 1502. In this case, theprocessor 1502 may access the memory 1503 through the network interface1501 or an I/O interface (not shown).

In the example of FIG. 15, the memory 1503 is used to store softwaremodules 1504 to 1506 for providing MEC service and a module 1507 forexchanging MEC-related control information. The virtualizationmanagement software 1504 is executed by the processor 1502 to virtualizehardware components including the network interface 1501, the processor1502, and the memory 1503 and provide Infrastructure as a Service (IaaS)or Platform as a Service (PaaS) facilities, thereby providing a hostingenvironment for one or more MEC applications 1506.

The application platform services software 1505 is executed by theprocessor 1502 to provide one or more MEC applications 1506 withmiddleware services such as a communication service, a radio networkinformation service, and a traffic offload function.

The one or more MEC applications 1506 are mobile edge applicationshosted on the MEC server 30. The one or more MEC applications 1506 usescommunication services provided by the application platform servicessoftware 1505 to communicate with a UE application running in a UE.

The module 1507 is executed by the processor 1502, and provides thefunction of the MEC server 30 for exchanging MEC-related controlinformation as described in the above embodiments.

Other Embodiments

Each of the above-described embodiments may be used individually, or twoor more of the embodiments may be appropriately combined with oneanother.

The above-described embodiments are merely examples of applications ofthe technical ideas obtained by the inventor. These technical ideas arenot limited to the above-described embodiments and various modificationscan be made thereto.

For example, the whole or part of the above embodiments can be describedas, but not limited to, the following supplementary notes.

(Supplementary Note 1)

A network apparatus, comprising:

at least one memory; and

at least one processor coupled to the at least one memory and configuredto:

-   -   incorporate edge computing related control information into a        header part of a protocol data unit of an encapsulation        protocol, the encapsulation protocol being used to encapsulate a        user packet originated from or destined for a radio terminal;        and    -   transmit the protocol data unit whose header part contains the        edge computing related control information.

(Supplementary Note 2)

The network apparatus according to Supplementary Note 1, wherein theedge computing related control information is to be sent from a serverto a radio access network node or vice versa, wherein the server isconfigured to provide one or both of computing resources and storageresources to a service or an application directed to the radio terminal.

(Supplementary Note 3)

The network apparatus according to Supplementary Note 2, wherein

the network apparatus is the radio access network node, or a corenetwork node located between the radio access network node and theserver, and

the edge computing related control information includes first controlinformation to be sent from the radio access network node or the corenetwork node to the server.

(Supplementary Note 4)

The network apparatus according to Supplementary Note 3, wherein thefirst control information includes at least one of: radio interfacequality; cell throughput; backhaul throughput; information about aservice used by the radio terminal; or priority information of the radioterminal.

(Supplementary Note 5)

The network apparatus according to Supplementary Note 2, wherein

the network apparatus is the server, and

the edge computing related control information includes second controlinformation to be sent from the server to the radio access network node.

(Supplementary Note 6)

The network apparatus according to Supplementary Note 5, wherein thesecond control information includes one or both of:

a radio resource control request requesting the radio access networknode to adjust radio resource management or radio resource scheduling ina radio access network; and

a traffic control request requesting the radio access network node toadjust traffic control for user packets to be sent from the radio accessnetwork to the server or a core network.

(Supplementary Note 7)

The network apparatus according to any one of Supplementary Notes 1 to6, wherein the encapsulation protocol is identical to an encapsulationprotocol used to transfer user packets of the radio terminal between acore network node and a radio access network node.

(Supplementary Note 8)

The network apparatus according to any one of Supplementary Notes 1 to7, wherein the encapsulation protocol is a General Packet Radio Service(GPRS) Tunneling Protocol for User Plane (GTP-U).

(Supplementary Note 9)

The network apparatus according to Supplementary Note 8, wherein theheader part includes:

a message type field indicating that the protocol data unit is aprotocol data unit carrying a user packet;

a next extension header type field indicating that the header partincludes a first extension header containing the edge computing relatedcontrol information; and

the first extension header containing the edge computing related controlinformation.

(Supplementary Note 10)

A method for a network apparatus, the method comprising:

incorporating edge computing related control information into a headerpart of a protocol data unit of an encapsulation protocol, theencapsulation protocol being used to encapsulate a user packetoriginated from or destined for a radio terminal; and

transmitting the protocol data unit whose header part contains the edgecomputing related control information.

(Supplementary Note 11)

The method according to Supplementary Note 10, wherein the edgecomputing related control information is to be sent from a server to aradio access network node or vice versa, wherein the server isconfigured to provide one or both of computing resources and storageresources to a service or an application directed to the radio terminal.

(Supplementary Note 12)

The method according to Supplementary Note 11, wherein

the network apparatus is the radio access network node, or a corenetwork node located between the radio access network node and theserver, and

the edge computing related control information includes first controlinformation to be sent from the radio access network node or the corenetwork node to the server.

(Supplementary Note 13)

The method according to Supplementary Note 12, wherein the first controlinformation includes at least one of: radio interface quality; cellthroughput; backhaul throughput; information about a service used by theradio terminal; or priority information of the radio terminal.

(Supplementary Note 14)

The method according to Supplementary Note 11, wherein

the network apparatus is the server, and

the edge computing related control information includes second controlinformation to be sent from the server to the radio access network node.

(Supplementary Note 15)

The method according to Supplementary Note 14, wherein the secondcontrol information includes one or both of:

a radio resource control request requesting the radio access networknode to adjust radio resource management or radio resource scheduling ina radio access network; and

a traffic control request requesting the radio access network node toadjust traffic control for user packets to be sent from the radio accessnetwork to the server or a core network.

(Supplementary Note 16)

The method according to any one of Supplementary Notes 10 to 15, whereinthe encapsulation protocol is identical to an encapsulation protocolused to transfer user packets of the radio terminal between a corenetwork node and a radio access network node.

(Supplementary Note 17)

The method according to any one of Supplementary Notes 10 to 16, whereinthe encapsulation protocol is a General Packet Radio Service (GPRS)Tunneling Protocol for User Plane (GTP-U).

(Supplementary Note 18)

The method according to Supplementary Note 17, wherein the header partincludes:

a message type field indicating that the protocol data unit is aprotocol data unit carrying a user packet;

a next extension header type field indicating that the header partincludes a first extension header containing the edge computing relatedcontrol information; and

the first extension header containing the edge computing related controlinformation.

(Supplementary Note 19)

A program for causing a computer to perform a method for a networkapparatus, wherein

the method comprises incorporating edge computing related controlinformation into a header part of a protocol data unit of anencapsulation protocol, the encapsulation protocol being used toencapsulate a user packet originated from or destined for a radioterminal.

(Supplementary Note 20)

The program according to Supplementary Note 19, wherein the edgecomputing related control information is to be sent from a server to aradio access network node or vice versa, wherein the server isconfigured to provide one or both of computing resources and storageresources to a service or an application directed to the radio terminal.

This application is based upon and claims the benefit of priority fromJapanese Patent Application No. 2017-076619, filed on Apr. 7, 2017, thedisclosure of which is incorporated herein in its entirety by reference.

REFERENCE SIGNS LIST

-   10 eNB-   20 S-GW-   30 MEC SERVER-   40 gNB-   50 UPF

1. A network apparatus, comprising: at least one memory; and at leastone processor coupled to the at least one memory and configured to:incorporate edge computing related control information into a headerpart of a protocol data unit of an encapsulation protocol, theencapsulation protocol being used to encapsulate a user packetoriginated from or destined for a radio terminal; and transmit theprotocol data unit whose header part contains the edge computing relatedcontrol information.
 2. The network apparatus according to claim 1,wherein the edge computing related control information is to be sentfrom a server to a radio access network node or vice versa, wherein theserver is configured to provide one or both of computing resources andstorage resources to a service or an application directed to the radioterminal.
 3. The network apparatus according to claim 2, wherein thenetwork apparatus is the radio access network node, or a core networknode located between the radio access network node and the server, andthe edge computing related control information includes first controlinformation to be sent from the radio access network node or the corenetwork node to the server.
 4. The network apparatus according to claim3, wherein the first control information includes at least one of: radiointerface quality; cell throughput; backhaul throughput; informationabout a service used by the radio terminal; or priority information ofthe radio terminal.
 5. The network apparatus according to claim 2,wherein the network apparatus is the server, and the edge computingrelated control information includes second control information to besent from the server to the radio access network node.
 6. The networkapparatus according to claim 5, wherein the second control informationincludes one or both of: a radio resource control request requesting theradio access network node to adjust radio resource management or radioresource scheduling in a radio access network; and a traffic controlrequest requesting the radio access network node to adjust trafficcontrol for user packets to be sent from the radio access network to theserver or a core network.
 7. The network apparatus according to claim 1,wherein the encapsulation protocol is identical to an encapsulationprotocol used to transfer user packets of the radio terminal between acore network node and a radio access network node.
 8. The networkapparatus according to claim 1, wherein the encapsulation protocol is aGeneral Packet Radio Service (GPRS) Tunneling Protocol for User Plane(GTP-U).
 9. The network apparatus according to claim 8, wherein theheader part includes: a message type field indicating that the protocoldata unit is a protocol data unit carrying a user packet; a nextextension header type field indicating that the header part includes afirst extension header containing the edge computing related controlinformation; and the first extension header containing the edgecomputing related control information.
 10. A method for a networkapparatus, the method comprising: incorporating edge computing relatedcontrol information into a header part of a protocol data unit of anencapsulation protocol, the encapsulation protocol being used toencapsulate a user packet originated from or destined for a radioterminal; and transmitting the protocol data unit whose header partcontains the edge computing related control information.
 11. The methodaccording to claim 10, wherein the edge computing related controlinformation is to be sent from a server to a radio access network nodeor vice versa, wherein the server is configured to provide one or bothof computing resources and storage resources to a service or anapplication directed to the radio terminal.
 12. The method according toclaim 11, wherein the network apparatus is the radio access networknode, or a core network node located between the radio access networknode and the server, and the edge computing related control informationincludes first control information to be sent from the radio accessnetwork node or the core network node to the server.
 13. The methodaccording to claim 12, wherein the first control information includes atleast one of: radio interface quality; cell throughput; backhaulthroughput; information about a service used by the radio terminal; orpriority information of the radio terminal.
 14. The method according toclaim 11, wherein the network apparatus is the server, and the edgecomputing related control information includes second controlinformation to be sent from the server to the radio access network node.15. The method according to claim 14, wherein the second controlinformation includes one or both of: a radio resource control requestrequesting the radio access network node to adjust radio resourcemanagement or radio resource scheduling in a radio access network; and atraffic control request requesting the radio access network node toadjust traffic control for user packets to be sent from the radio accessnetwork to the server or a core network.
 16. The method according toclaim 10, wherein the encapsulation protocol is identical to anencapsulation protocol used to transfer user packets of the radioterminal between a core network node and a radio access network node.17. The method according to claim 10, wherein the encapsulation protocolis a General Packet Radio Service (GPRS) Tunneling Protocol for UserPlane (GTP-U).
 18. The method according to claim 17, wherein the headerpart includes: a message type field indicating that the protocol dataunit is a protocol data unit carrying a user packet; a next extensionheader type field indicating that the header part includes a firstextension header containing the edge computing related controlinformation; and the first extension header containing the edgecomputing related control information.
 19. A non-transitory computerreadable medium storing a program for causing a computer to perform amethod for a network apparatus, wherein the method comprisesincorporating edge computing related control information into a headerpart of a protocol data unit of an encapsulation protocol, theencapsulation protocol being used to encapsulate a user packetoriginated from or destined for a radio terminal.
 20. The non-transitorycomputer readable medium according to claim 19, wherein the edgecomputing related control information is to be sent from a server to aradio access network node or vice versa, wherein the server isconfigured to provide one or both of computing resources and storageresources to a service or an application directed to the radio terminal.